home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000042_lindberg@cs.colgate.edu_Mon Sep 27 14:32 MDT 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
7KB
Received: from yvax2.byu.edu by maine.et.byu.edu; Mon, 27 Sep 93 14:32:14 -0600
Return-Path: <lindberg@cs.colgate.edu>
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3G2STWTJK935UU7@yvax.byu.edu>; Mon, 27 Sep 1993 14:30:01 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3G2SNRIPS9360HV@yvax.byu.edu>; Mon, 27 Sep 1993 14:29:52 MDT
Received: from yvax2.byu.edu by alaska.et.byu.edu; Mon, 27 Sep 93 14:31:30 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H3G2RU9SB4935UU7@yvax.byu.edu>; Mon, 27 Sep 1993 14:29:14 MDT
Received: from cs.colgate.edu (csnext.colgate.edu) by yvax.byu.edu (PMDF
V4.2-13 #4169) id <01H3G2RAOOCG94HM2Q@yvax.byu.edu>; Mon,
27 Sep 1993 14:28:48 MDT
Received: from woody (woody) by cs.colgate.edu (NeXT-1.0 (From Sendmail
5.52)/NeXT-2.0) id AA12135; Mon, 27 Sep 93 16:31:21 EDT
Received: by woody (NX5.67c/NeXT-2.0) id AA13534; Mon,
27 Sep 93 16:31:18 -0400
Received: by NeXT.Mailer (1.87.1)
Received: by NeXT Mailer (1.87.1)
Date: Mon, 27 Sep 1993 16:31:18 -0400
From: lindberg@cs.colgate.edu
Subject: Re: MiscKit summary and proposal: stirring up the ashes
To: misckit@cs.colgate.edu
Reply-To: lindberg@csnext.colgate.edu
Message-Id: <9309272031.AA12135@ cs.colgate.edu >
Content-Transfer-Encoding: 7BIT
Status: O
Well, guess I can send this along now....
--------------
(1) Prefixes.
Yeah, "Misc" would do very nicely. I think the
main problem people have with prefixes of over two
letters is one of pronunciation: a random selection
of over two letters can be hard to pronounce. But
since "Misc" is a one-syllable thing anyways, I doubt
there should be too much problem....
(2) Licensing issues.
Yech. I'd agree, though...I don't think PD is
the route to go. But don't ask me for the legalese...
(3) Maintaining source.
This sounds reasonable.
(4) Commercial apps that use the MiscKit:
Hmm... how about...
Required:
An acknowledgement of the use of the MiscKit.
It would be nice, but not required:
A pointer to where the MiscKit could be found
(in docs or if asked, whatever)
Providing source to whoever asks for it
I think that's basically what was suggested anyways...
(5) CDROM distributions:
(6) Third party distributions:
Sounds good to me....(Geez, how many pages of legalese
will all this be?)
(7) Modified distributions must be labelled as such.
Hmmmm.... *IF* you want to allow these, then
they should definitely be clearly marked.
I would prefer to just have people send in additions
to be included in the official MiscKit. There'll
probably be enough versions of the official MiscKit
lying around eventually that it'll probably be
confusing enough without the addition of several
different versions muddling the picture as well.
If they are allowed, how about say that Don has to
give permission? Hopefully that will cut down on
the number.... and maybe Don can convince them to
just contribute to the MiscKit instead :-)
(8) People who modify the source do NOT have to send the
mods back to the list:
Agreed. But mention that it would be really nice
if they did... :-)
(9) What will be accepted into the kit?
Sounds good. I doubt we'll run into too much
trouble on this front.
(10) For now, it will be up to a developer to make sure
that any MiscKit resources are included as part
of an app, in the app wrapper.
Sounds good too. Hopefully most things like tiffs
will be in a palettized class, which if you just use
the palette (or the whole library...right?) the tiff
should be already included. (Correct me if I'm wrong.)
(11) Each contributor will be recognized
Sounds good to me.
(12) Object "owner's" responsibilities
Also sounds reasonable.
(13) I'd like to have a file at the top level, a sort of
"to do" list
This is probably a good idea too.
(14) Backward compatibility:
This also sounds good. But this means it pays
to get it as good as you can the first try.
As someone mentioned, it would be a really good
idea to send the class definition to the list first
to see if anyone has any suggestions.
I personally prefer /LocalDeveloper and ~/Developer as
installation directories, mainly because the MiscKit
is a development tool, not a finished end product like
an app. Admittedly though, /LocalLibrary
and ~/Library are much more likely to exist on a given
system. Perhaps an option for either? I suppose this
is the thing symlinks were made for in any event...
(Is there any way to use Installer.app for this? Or
should we not assume execute access to it?)
A question here, I guess, is whether we should keep all
the pieces of the MiscKit together in its own structure,
or split it up with a /MiscKit subdirectory in every
approprite spot:
LocalDeveloper/Apps
/Demos/MiscKit/[all example apps, if any]
/Examples/MiscKit/[all .m files, etc]
(or would ../Classes/MiscKit be better?)
/Palettes/MiscKit/[all .palette's]
/Headers/MiscKit/[all .h files]
/Documentation/MiscKit/[all .rtf files]
etc...
or
../MiscKit/Demos
/(Examples | Classes)
/Headers
/Documentation
/Palettes
etc...
and just put the /MiscKit subdirectory somewhere like
/LocalDeveloper?
It definitely should be possible to just include one
or two of the classes singly without having to drag in
the whole library. I'm not sure what the directory structure
would have to look like, but if I want to include just one
class I'd like to be able to do it with minimal effort.
I suppose this is the place where self-encapsulation is
important... sometimes, though, it's probably just going
to be up to the programmer to make sure all necessary files
are in their project. Make sure the documentation is clearly
marked in any situation such as this.
I agree (sorry Don) with the school which thinks that
every app should be self-contained, i.e. no dependencies
on outside files other than NeXT-supplied ones. Basically,
if you write an app using some of these things as a pooled
resource, and Joe User at xxxx.edu downloads your
Excellent.app, they probably won't be able to run it because
they don't have MiscKit installed. Most likely, the reaction
will simply be `bag it' and delete Excellent.app rather than
go to the trouble to find, download, and correctly install
the whole MiscKit just to have a couple tiffs or nibs. It
just leaves one more thing to go wrong when. If it's in the
app, then you can be sure.
I can understand the sysadmin tendencies in wanting to save
disk space in any way, but virtually always the little extra disk
space needed will far offset all the potential problems
that could arise.
Phew. Well, that's all for now,
Carl Lindberg
+---------------------------------------------------+
|Carl Lindberg Colgate University '94 |
|clindberg@colgateu.bitnet |
|clindberg@center.colgate.edu |
|lindberg@csnext.colgate.edu (NeXTMail welcome) |
+---------------------------------------------------+